-
Notifications
You must be signed in to change notification settings - Fork 4.8k
HIVE-29234: Iceberg: Validate HMS REST Catalog Client with OAuth2 #6124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
b200287 to
b5bccec
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall, +1
Please follow the addressable advice from SonarQube.
https://sonarcloud.io/project/issues?id=apache_hive&pullRequest=6124&issueStatuses=OPEN,CONFIRMED&sinceLeakPeriod=true
I changed the JIRA ticket number in the title because I suspect HIVE-29234 is probably the intended one. Please revert it if I'm wrong
| .replace("OAUTH2_JWKS_URI", getJwksUri()) | ||
| .replace("OAUTH2_CLIENT_ID", OAUTH2_SERVER_ICEBERG_CLIENT_ID) | ||
| .replace("OAUTH2_CLIENT_SECRET", OAUTH2_SERVER_ICEBERG_CLIENT_SECRET) | ||
| // .replace("localhost", "host.docker.internal") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we remove this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, it was a leftover that I didn't notice, done.
|
|
Thanks for core review, @okumin! |



What changes were proposed in this pull request?
Added Java integration test for testing HMSRestCatalogClient with Oauth2 mode and changed existing RESCatalog client q-tests (those that use HMS and Gravitino as a server) to use Oauth2.
Why are the changes needed?
To test HMSRestCatalogClient with Oauth2 so that it could be used in production systems.
Does this PR introduce any user-facing change?
No, this PR only adds/updates tests.
How was this patch tested?
New and existing tests.